refactor: VM receives bootstrap address as runtime parameter#260
Merged
refactor: VM receives bootstrap address as runtime parameter#260
Conversation
zharinov
changed the title
zharinov
force-pushed
the
refactor/bootstrap-header
branch
3 times, most recently
from
49ccd99 to
a1578d8
Compare
zharinov
force-pushed
the
refactor/bootstrap-header
branch
from
a1578d8 to
173033c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bootstrap: StepIdparameter toVM::execute()andVM::execute_with()StepId(0))Why
Decouples VM from compile-time preamble choice. The same module can be executed with different preambles depending on the use case (e.g., root-match vs recursive deep-search). Selection logic lives in the caller, not the bytecode.